Important: For more detailed information on IPCF and configuration example, please refer the IPCF Administration Guide.|
•
|
IPCF Name: is the name of IPCF. User can specify any name by which this IPCF is to be identified.
|
|
•
|
IP Address: is the IOP address (IP address for CORBA communication) of the machine running IPCF suite. The user can retrieve it by executing the “show orbem status” command on CLI of IPCF machine. A sample output of this command is shown below:
|
|
•
|
Port Number: is the TCP port over which the CORBA communication occurs with the IPCF. This setting must be identical to the IIOP port setting on the IPCF. It can also be retrieved using the “show orbem status” command as shown above.
|
Important: Alternatively, the IP address and Port number can be taken from the IPCF administrator.
Caution: In case of the co-location of the Web Element Manager (WEM) and PPT, either WEM has to be installed before PPT so that port 5432 is not available or PPT PostgreSQL should not be installed on port 5432. This is because the port is fixed at 5432 for WEM.|
•
|
Application Server ID: is the name by which the PPT is identified to the IPCF server. The user can retrieve it by executing the “show orbem client table” command on the IPCF machine. It is set by executing following set of (sample) commands on command line interface in EXEC Mode:
|
[local]asr5000#configure
You can get this information by executing the “show configuration” command. The sample output of this command is shown below:
Caution: If the WEM and PPT are co-located, you have to make sure that the application server IDs are different for WEM and PPT for CORBA management.|
•
|
Application Server Password: is the password set for the ORBEM client configuration as shown in the above sample set of command lines. It is used by the PPT when communicating with the IPCF.
|
Important: Alternatively, the application server ID and password information can be taken from the IPCF administrator.|
•
|
Node Type: for the IPCF can be specified as Primary or Secondary. Only one IPCF can be specified as Primary in PPT. One IPCF has to be Primary, because it is the primary IPCF from which the information is fetched including IPCF objects like profile-policy, QoS-profiles, data-services, timedefs etc. While configuring IPCF objects, a primary IPCF has to be selected, and secondary IPCFs can optionally be selected.
|
Important: In PPT-SSC communication, the XML RPC protocol uses HTTP as the data transport mechanism.|
•
|
SSC Name: is the name of the machine where SSC is installed.
|
|
•
|
Main SSC IP Address: is the IP address of the interface on which main SSC's apache server (profile controller application) is installed and running.
|
Important: In a geographic redundant setup, there will be two physical SSCs, each addressable with a different IP address. The two different IP addresses are main and standby IP address. In case of a failover to the redundant SSC, user has to manually change the standby node to active. There is no automatic detection of a failover and therefore once the main node comes up back, user has to manually change that back to active.|
•
|
Port Number: is the port over which communication occurs with the SSC. On the SSC, this is the port on which the Apache Web server runs. The Apache port is set to 8080 by default.
|
|
•
|
Standby SSC IP Address: is the IP address of the interface on which standby SSC's apache server (profile controller application) is installed and running. This IP address can be obtained through ‘Listen’ configuration variable in the Apache configuration file “httpd.conf”.
|
|
•
|
Port Number: is the port over which communication occurs with the standby SSC. On the SSC, this is the port on which the Apache Web server runs. The Apache port is set to 8080 by default.
|
Important: IP address and Port information can be retrieved through the Apache configuration file httpd.conf. Alternatively you can contact the SSC administrator for this information.
Important: After installation a user is added to the PPT database. The login credentials of this user can be used to create other application users. It is recommended that you change the password for this user on first login. Please contact Cisco support for the default username and password. The default session timeout for this user is 15 minutes.|
•
|
Level 1: Choosing this option, the user can collect logs for application, application installation, Web server, and database.
|
|
•
|
Level 2: Choosing this option, the user gets all the debug logs collected using Level 1, to the database.
|
Important: For more information on PPT traps, please refer the IPCF PPT Application MIB chapter of the Cisco ASR5000 Series SNMP MIB Reference guide.